--- title: "Create Biometric Authentication" method: POST path: "/v1/clients/{clientId}/verifications (Biometric Authentication)" tags: ["Biometric Authentication"] --- # Create Biometric Authentication `POST /v1/clients/{clientId}/verifications (Biometric Authentication)` Use this endpoint to create a Biometric Authentication case with the `clientId` from a previous successful Identity Verification case.

Important **Important:** Before using this endpoint, see the integration guide.
Note **Note:** Client Authentication has been renamed to Biometric Authentication. Biometric Authentication is supported in both V1 and v2 integrations. ## Path parameters - `clientId` string, required ## Headers - `Authorization` string, required — The `access_token` returned in your most recent [Create access token](https://docs.fourthline.com/reference/create-access-token) response. ## Request body - object - `providerProcessId` string, required — Your unique identifier for the case.

**Tip:** To create multiple cases for the same `clientId`, you must specify a unique `providerProcessId` for each separate case. - `processType` string, required — The case type: `ClientConfirmation`= Biometric Authentication case - `branch` string — Your configuration for this product.
Set the string provided by your Fourthline delivery manager.
If **not** set, we use your default configuration.

**Tip:** Use this parameter for case configuration in older setups. - `clientData` object, required — The client’s identity data. - `person` object — The client’s personal data.

Requirements: For API integration object is required. - `type` string, required — The type of entity the client is.
Enum:
• `Legal Entity`: The client is a company or organization with legal rights and obligations.
• `Legal Person`: The client is a non-human entity with legal rights and obligations.
• `Natural Person`: The client is a living human. - `name` string — The client’s full name.

Format: Alphabetical characters, spaces, hyphens, and apostrophes

Example: John James Smith
**Configurable**: You can configure this parameter to be required or optional on request - `initials` string — The client’s initials.

Format: Alphabetical characters

Example: JCCF - `firstName` string — The client’s first name.

Format: Alphabetical characters, spaces, hyphens, and apostrophes

Example: John - `middleName` string — The client’s middle name(s).

Format: Alphabetical characters, spaces, hyphens, and apostrophes

Example: James - `lastName` string — The client’s last name.

Format: Alphabetical characters, spaces, hyphens, and apostrophes

Example: Smith - `otherLastName` string — Any other last name the client uses, e.g. married name.

Format: Alphabetical characters, spaces, hyphens, and apostrophes - `nationality` string — The client’s nationality.

Format: ISO 3166-1 alpha-3 country code

Example: BEL - `gender` 'Female' | 'Male' | 'Other' | 'Unknown' — The client’s sex

Format: Case sensitive
Enum:
• `Female`: Female in line with ID document
• `Male`: Male in line with ID document
• `Other`: ID document contains a value other than `Male` or `Female`
• `Unknown`: ID document contains **no** gender field - `birthDate` string — The client’s date of birth.

Format: Date YYYY-MM-DD

Example: `1960-10-18`= October 18, 1960 - `placeOfBirth` string — The city where the client was born.

Format: Alphabetical characters, spaces, hyphens, and apostrophes

Example: Sint-Agatha-Berchem
**Configurable**: You can configure this parameter to be required or optional on request - `countryOfBirth` string — The country where the client was born.

Format: ISO 3166-1 alpha-3

Example: BEL - `address` object — The client’s address details.

Requirements: For API integration that upload `person` and `emailAndPhone` data. - `street` string — The street of the client’s address.

Format: Alphabetical characters, spaces, hyphens, and apostrophes

Example: Rue Jean-Baptiste Jansen - `streetNumberPrefix` string — The prefix of the street number

Example: A1 - `streetNumber` integer — The street number of the client’s address.

Format: int32 greater than or equal to zero - `streetNumberSuffix` string — The suffix of the street number.

Format: Alphabetical characters, spaces, hyphens, and numerals

Example: 123A - `postalCode` string — The zip code of the client’s address.

Format: Alphabetical characters, spaces, hyphens, and apostrophes

Example: 1082

**Note**: We use Google’s Address Validation API and depend on the quality of their data - `region` string — The region of the client’s address

Format: Alphabetical characters, spaces, hyphens, and apostrophes

Example: Brussels Capital Region - `city` string — The city of the client’s address.

Format: Alphabetical characters, spaces, hyphens, and apostrophes

Example: `London` - `country` string — The country of the client’s address.

Format: ISO 3166-1 alpha-3

Example: BEL - `emailAndPhone` object — The client’s email address and phone number(s). - `email` string — The client’s email address.

Format: Maximum 254 characters [_-a-zA-Z0-9.+]+@a-zA-Z0-9

Example: `j.smith@example.com` - `phone` string — The client’s landline number.

Format: Must include the country code and begin with `00` or `+` **without** spaces

Example: 003281123456 **or** +3281123456 - `mobile` string — The client’s mobile phone number.

Format: Must include the country code and begin with `00` or `+` **without** spaces

Example: `00324123456789` **or** `+324123456789` - `deviceMetaData` object — The metadata from the client’s device. - `browserType` string — The type of browser the client’s device is using.

Example: Google Chrome - `browserVersion` string — The version of the browser the client’s device is using.

Example: 116.0.5845.172 - `ipAddress` string — The IP address of the client’s device.

Example: 185.128.27.102 - `language` string — The language of the client’s device.

Format: ISO 3166-1 alpha-2

Example: `NL` - `latitude` string — The latitude of the client’s device geolocation

Format: Float between -90 and 90

Example: 45.464664 - `longitude` string — The longitude of the client’s device geolocation.

Format: Float between -180 and 180

Example: 9.188540 - `model` string — The model of the client’s device.

**Tip:** **Required** for workflows that include Qualified Electronic Signature, so that we can check it matches the client’s Identity Verification case.

Example: OnePlus Nord CE 5G - `osCompromised` string — Whether the operating system of the client’s device is compromised. - `osVersion` string — The version of the operating system of the client’s device.

Example: Android 13 - `region` string — The country code of the client’s device geolocation.

Format: ISO 3166-1 alpha-2, e.g. `IT` **or** ISO 3166-1 alpha-3, e.g. `ITA` - `sdkVersion` string — The version of the SDK used.
Set to `v1`. - `analyticsId` string — The identifier for the metadata analytics. ## Response `201` Biometric authentication created - object - `verificationId` string — Our unique identifier for the case.

Format: uuid string

Example: `790f325a-48c9-4b82-bb53-c0ea128236f0`
Validations: uuid format, `verificationId` exists
Errors: Format is incorrect or doesn’t exist - `providerProcessId` string — Your unique identifier for the case. - `status` string — The [case status](https://docs.fourthline.com/docs/biometricauth-statuses). ## Other responses - `400` — Invalid request parameters - `404` — Biometric authentication case not found - `422` — The request could not be processed --- [API](https://skmtc.net/fourthline/apis/fourthline-apis.md) · [All operations](https://skmtc.net/fourthline/apis/fourthline-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/fourthline/fourthline-apis/revisions/7991ae7c8383/schema)